Managing Endpoint Profiles

Endpoint profiles determine which configurations apply to a device and when. Use profiles to group related configurations, target them to the right endpoints, and control the order in which policies apply.

Add a new profile

1. Profile Details
   1. Navigate to Endpoints → Profiles and click on Add Profile.
   2. Enter a unique name and a descriptive purpose for the Profile. Click Next.
2. Targeting and Priority
   1. Define targeting using the UI builder or switch to CEL (Common Expression Language). The UI builder provides fields like Hostname and OS with AND/OR operators; the CEL editor supports fields such as e.hostname, e.os, and e.machine_serial_number.
   2. Set the Priority to resolve overlaps. The value can range from 1 to 1000,where a higher value takes precedence. Click Next.
3. Configurations, Uninstall Protection, and Overrides
   1. Set the configurations for Performance, Content Inspection, Detection, Software Update, and Policy. These are the reusable default or custom configurations from the Configurations page. The default configurations are automatically selected. See, Configurations.
   2. Optionally enable Uninstall Protection to require a password to uninstall the Endpoint Sensor. This is a per-Profile setting.
   3. Optionally add Overrides for advanced, low-level settings that are not exposed in the UI. Overrides use flattened JSON and should be used sparingly. Click Next.
4. Review the profile and click Save.

The saved profile is displayed on the Profiles page. Endpoints that register and match your targeting automatically receive this profile.

Duplicate an existing profile

Duplicating saves time when you need a new profile that closely mirrors an existing one.

1. From the profiles list, click on the actions menu and select Duplicate.
2. Update the profile name and description to reflect the new purpose.
3. Adjust any configurations or targeting rules that should differ from the source profile.
4. Save the profile and review its priority to make sure it lands in the correct order.

note

Profiles migrated from the legacy Endpoint Sensors page are read-only and cannot be edited. To make changes, you must recreate the profile or duplicate an editable profile.

Edit profile settings

• Configurations: Swap in updated configuration objects whenever performance or policy requirements change. Remember that configuration updates can affect other profiles that reference the same object.
• Targeting rules: Modify or add criteria to expand or narrow the devices that qualify. Conditional logic is evaluated dynamically, so changes take effect as soon as you save.
• Priority: Drag and drop the profile in the list to adjust priority. Higher priority profiles win when multiple profiles target the same device.

All edits are tracked in the activity log so you can audit changes and confirm who modified a profile.

Remove a custom profile

To prevent a custom profile from applying, delete it and rely on the next highest-priority profile.

1. From the profiles list, click on the actions menu and select Delete profile. Click Confirm to complete the action.
2. Verify that affected devices inherit the appropriate fallback profile.

note

Only profiles you created can be deleted. Migrated or default profiles remain read-only and cannot be removed.

Best practices

• Review profile coverage regularly to ensure every device matches at least one active profile.
• Keep targeting rules as specific as necessary to avoid unintended overlaps.
• Maintain a clear naming convention and documentation for profiles and configurations so future administrators understand the intent.
• Test significant changes in a limited scope by cloning a profile, adjusting targeting, and validating on a small device group before broad deployment.